docs: EKS cluster governance at scale — status, roadmap, and AI agents #2
+100
−27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Post-demo design document capturing current state, gaps, and the full roadmap for governing and scaling the EKS cluster fleet.
What's in this doc
clusters/<name>/main.tfserves both as cluster metadata and injection location map, the_apps-adsd-eksaccount repo patternrepo_namefromcluster_nameclusters/intoclusters/<lifecycle>/<team>/<name>/hierarchy; threadteam/lifecycleparams through SC → Lambda → CodeBuildupdate_all_clusters.pywith--lifecycle,--team,--forceflagsFollows the May 14 GitHub Provisioning Pipeline Demo (Manuel, Matthew, David, Delong).